-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extract websocket functionality that is common to both server and future client #2582
base: master
Are you sure you want to change the base?
Conversation
@xemul Just a friendly ping. |
4c3bfeb
to
f044136
Compare
@xemul Just a friendly ping. |
@xemul Just a friendly ping. As far as I'm aware this PR only needs merging, the review has already been done. |
f044136
to
f3becb2
Compare
Rebased on top of latest master. |
Still conflicts |
5f5c9ba
to
19da320
Compare
19da320
to
74c8730
Compare
@xemul Rebased again, should be good to merge. Thanks! |
This will allow to implement Websocket client that reuses existing code.
Current implementation of websocket connection is specific to the server. Rename to more appropriate name.
Websocket connection handling is mostly not specific to the server and thus can be reused on the client easily.
Previous name was useful when it's used locally in translation unit. The new name is exposed in a header and should be more unique.
This function will be useful on websocket client to construct Sec-WebSocket-Key header.
74c8730
to
ba4d044
Compare
Rebased again. |
@xemul Just a friendly ping. The PR is ready for merging and was not merged in the past due to merge conflicts. |
@scylladb/seastar-maint hello maintainers, could you help review / merge this change? |
@xemul Just a friendly ping.. |
Currently websocket server embeds a lot of functionality that would be useful for websocket client. This PR extracts it into a form that is easier to reuse. The websocket client itself has been implemented in #2552.
This PR extracts parts of #2552 to make it easier to land.